Closed
Conversation
Update naming conventions
Updated license information to reflect dual licensing under MIT and Apache 2.0.
Added the Apache License 2.0 text to the repository.
Member
|
I think this branch needs a rebase |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
see issue #40
Summary
Add longchat-specific SHACL shapes to
shapes/chat.ttlwithout changing the existing published chat shapes.What Changed
LongChatChannelShapeformee:LongChatchannelsLongChatMessageShapefor signed chat messages with append-only replacement linksAppendOnlyMessageVersionShapefor message version chains viadct:isReplacedByDeletedLongChatMessageShapefor replacement messages carrying deletion timestampsLongChatThreadShapeforsioc:Threadreply structuresLongChatActionShapefor sentiment/action nodes targeting chat messageshttps://schema.org/and legacyhttp://schema.org/predicates for compatibility with existing datasec:proofValuecurrently signs the core message fields onlyWhy
The current SolidOS long chat implementation stores richer chat data than the legacy chat shapes describe:
YYYY/MM/DD/chat.ttl)sioc:Threadhttp://schema.org/in deployed chat dataThese additions model that behavior as new semantic variants inside the existing chat domain, while preserving the existing
Chat*shapes unchanged.Compatibility
Chat*shape was renamed or modified incompatiblyhttp://schema.org/data remains validhttps://schema.org/data is also acceptedValidation
Validated successfully with:
python3 scripts/validate-shacl-shapes-file.py shapes/chat.ttlpython3 scripts/check-namespaces-and-names-file.py shapes/chat.ttlpython3 scripts/check-metadata-and-immutability-file.py shapes/chat.ttl